5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
- Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 2-1: Data Dictionary Overview

Some Examples of Domains


Domains are designer-defined to satisfy the requirements of a specific application or system of applications. A domain can provide a pattern for a specific field in an application, or a category of fields.

A Product Number domain, for example, can describe the attributes of a Product Number field wherever it occurs in an application. You may even assign the same name to a domain and to a field. Zip codes, customer numbers, and vendor numbers are additional examples of domain definitions that relate to specific fields.

An Amount domain, on the other hand, might be linked to a virtually unlimited number of fields and work fields in the system, such as Invoice Amount, Inventory Amount, Order Amount, Requisition Amount, Line Item Amount, Amount to Pay, and so on. Such domains are generically named, and usually do not share a name with a specific field. Accounts and addresses are additional examples of domain definitions that relate to a variety of fields in an application or in the system.

Application Design Manual                                         "Powered by Appx Software"

112

©2006 By APPX Software, Inc. All Rights Reserved